Communication method, mobile network system, and node apparatus that manages a bearer

专利摘要:
METHOD OF COMMUNICATION IN A MOBILE NETWORK SYSTEM, MOBILE NETWORK SYSTEM AND NODE DEVICE. A system, method and apparatus that allow instantaneous restoration of communication services responsive to an arrival at a mobile terminal after restart of a mobility management node are disclosed. A bearer management node maintains specific bearers for re-establishing communication services, while removing other bearers.
公开号:BR112012019257B1
申请号:R112012019257-4
申请日:2011-04-27
公开日:2022-01-25
发明作者:Junya OKABE；Toshiyuki Tamura
申请人:Nec Corporation；
IPC主号:

专利说明:

technical field
[0001] This invention relates to a communication network and more particularly to a system and method as well as an apparatus which can be applied to take advantage of the next generation EPC (Evolved Packet Core) mobile network system.
[0002] The following cites certain abbreviations used in this specification. CS: Circuit Switched CSFB: Circuit Switched Backward e-NodeB (eNodeB): Evolved Node B G-MSC: Mobile Switching Gateway GPRS: General Packet Radio Services GTP-C: (Tunnel Protocol Control Plane) GPRS) GTP-U: (GPRS Tunnel Protocol User Plan) P-MIP: Proxy Mobile Internet Protocol HSS: Domestic Subscriber Server IMS: IP Multimedia Subsystem IMSI: International Mobile Station Signature Identifier ISR: Idle Mode Signaling Reduction LTE: Long Term Evolution MME: Mobility Management Entity MSC: Mobile Switching Center MTC: Machine-Type Communication P-GW: (PGW or PDN-GW): PDN Packet Data Network Gateway : Packet Data Network QCI: Class Identifier QoS RAI: Routing Area Identity RNC: Radio Network Controller S-GW (or SGW): Gateway in Service SGSN: Node GPRS Support in Service SMS: Messaging Service Short SCPT: Flow Control Transmission Protocol TA L ist: Tracking Area List TAU: Tracking Area Update TEID: Tunnel Endpoint Identifier GRE key: Generic Routing Encapsulation Key UE: UMTS User Equipment: Universal Mobile Telecommunications System VLR: 3G Visited Location Recorder : Third Generation 3GPP: 3rd Generation Partnership Project prior art
[0003] EPC Next Generation Mobile Networking System is a network architecture that accommodates 3G (third generation mobile communication system), LTE and so on in a network. The following describes various network nodes.
[0004] An MME is a mobility management node. In LTE radio access, the MME takes care of mobility management (mobility control), such as tracking a mobile station UE in idle mode, authenticating and preparing a user data transmission path between an S-GW and a base station e-NodeB, in LTE radio access. A mobile station is also called 'a user device', 'a mobile terminal', or simply 'a terminal'. The MME is involved in tracking and locating UEs in idle mode or in bearer activation/deactivation processes. MME selects S-GW at the time of UE frequency transfer in LTE and performs user authentication along with HSS. It is noted that a bearer means a logical packet transmission path preparation between e-NodeB and S-GW/P-GW or similar.
[0005] An SGSN is a mobility management node in the 3G core network. It is a packet switching unit that takes care of mobility management for mobile stations, such as in-service subscriber management, in-service subscriber mobility management, call origination/arrival control, tunnel control, load control , QoS (Quality of Service) control or similar.
[0006] When a mobile terminal (UE) is in an idle or power-saving (Idle-LTE) state on an LTE core network, the mobile station (UE) is identified in the precision corresponding to a list of area screen (TA List) composed of a plurality of cells (MME maintains the most recent updated Ta List). At the instant of a call arriving at the mobile station, location is performed using the last recorded TA List. The SGSN of the 3G core network performs localization in an RA (Routing Area).
[0007] An S-GW performs routing and transmission of a user data packet. The S-GW is a bearer management node that manages the context of a mobile station UE (an IP bearer service parameter or similar). In response to a bearer definition request from an MME that has received an attach request from the mobile station UE, the S-GW defines a path definition request for a bearer P-GWe in the direction of an e- At the.
[0008] The S-GW also executes a location trigger when downlink (DL) data to a terminal has arrived.
[0009] A P-GW takes care of a connection from a mobile station (also called a UE, a user device or a mobile terminal) to a packet data network (a network of services: web browsing services or a external network, such as IMS or similar).
[0010] The following describes the reset of MME/SGSN.
[0011] MME/SGSN 'restart' or restart' means the termination of service due to failure, or intentional termination of service for maintenance, which leads to the initialization setting operation in the MME/SGSN, as a result of which, subscriber information or bearer information that is necessary for the operation of the MME/SGSN to operate is lost.
[0012] Non-Patent Document 2 (3GPP TS 23.007) provides that when the S-GW detects that an MME/SGSN has restarted, the S-GW shall release the bearer context of a UE mobile station registered in the MME/SGSN that restarted. That is, according to Non-Patent Document 2, when the MME restarts after failure, the MME removes all bearer contexts affected by the restart. When the S-GW detects that the MME has restarted, the S-GW removes the PDN connection table/bearer context corresponding to the MME that restarted and frees up internal resources relevant to the PND connection.
[0013] Assuming that an S-GW operates in accordance with the above specification of Non-Patent Document 2, when the MME operation has restarted, the S-GW is unable to perform a packet arrival operation for a mobile station UE until it originates a call by the mobile station itself or periodic location registration (eg, Attach Request/TAU) periodically by the mobile station itself with the MME.
[0014] When there is a call coming to the mobile station UE, the network performs locating at the same time for all cells associated with an area where the mobile station UE has made the location registration (tracking area). The mobile station UE thus located accesses a serving cell and establishes a call. However, as per the specification of Non-Patent Document 2, all information or features of the restarted MME holder have already been removed or released. That is, in the S-GW, radio access bearers in the direction of the S-GW to the e-NodeB and session information between the MME and the S-GW have been removed or released, such that when packet data arrives for the mobile station UE are received only for no purpose.
[0015] In the S-GW in this state, TEID or GRE Key, as the tunnel identification information (GTP-U or P-MIP), a transport protocol between the S-GW and P-GW, has also been removed. Therefore, in S-GW the incoming data is rejected. The P-GW also removes relevant features in response to the rejection of packet data arriving from the S-GW. Prior art document patent document Non-Patent Document 1:
[0016] 3GPP TS 23.203 V9.4 (2010-03) 3rd Generation Partnership Project: Technical Specification Group Services and System Aspects: Load Control Architecture and Policy (Version 9), page 31, Table 6.1. 7: Standardized QCI Features Non-Patent Document 2:
[0017] 3GPP TS 23.007 V9.3.0 (2010-03) 3rd Generation Partnership Project: Technical Specification Group Core Network and Terminals; restore procedures (Version 9), pages 27-28 Non-Patent Document 3:
[0018] 3GPP TS 23.272 V9.3.0 (2010-3) 3rd Generation Partnership Project: Services of the Technical Specification Group and System Aspects; Circuit Switched (CS) Rewind in Evolved Packet System (EPS); Stage 2 (Version 9) pages 26-27. Summary of the invention Problems to be solved by the invention
[0019] The disclosures of Non-Patent Documents 1 to 3 are incorporated by reference into the present specification. The following is a review of related techniques.
[0020] If the S-GW operates in accordance with the above specification of Non-Patent Document 2, as described above, the S-GW that detected the restart of the MME/SGSN mobility management node releases the entirety of the mobile station bearers UE registered in the MME/SGSN when the restart took place.
[0021] Therefore, reception to the mobile station UE after the MME/SGSN mobility management node restart may not be reported to the mobile station UE until such time that the attach operation for registration in the network is performed in the mobile station HUH. That is, if during the time that elapses after the restart of the MME/SGSN until the end of the attach operation, triggered by the origination by the mobile station UE itself or the periodic location registration by the mobile station UE, the mobile station UE is unable to have a communication service, even if there is a communication service reception. For example, during a periodical location log time interval (e.g. 45 minutes) at most following MME/SGSN restart, incoming packet data forwarded to the mobile station UE cannot be provided for the mobile station UE.
[0022] That is, a packet communication service is stalled. This presents a serious problem as communication services such as social infrastructure cannot be received for a pre-defined time if IMS is exploited in an EPS network.
[0023] Consequently, it is an objective of the present invention to provide a system, a method and an apparatus that allow accelerating the restoration of communication services to a mobile station after the restart of a mobility management node. Means of solving problems
[0024] In accordance with one aspect of the present invention, a communication method is provided in which a bearer management node maintains a specific eligible bearer for re-establishing communication services, and removes the other bearers. If a mobility management node is restarted, the bearer management node maintains at least one bearer.
[0025] According to another aspect of the present invention, a communication method is provided where, upon restart of a mobility management node, a circuit-switched node sends to the mobility management node a notification message including identification information associated with a mobile station and location registration area information, and the mobility management node initiates locating, including identification information associated with the mobile station, for an area corresponding to the registration area information of place.
[0026] In accordance with the present invention, there is also provided a mobile network system in which a bearer management node maintains a specific eligible bearer for the restoration of communication services, and removes other bearers. The mobile network system includes a mobility management node and a bearer management node. When the mobility management node restart is performed, the bearer management node keeps at least one of the bearers as defined.
[0027] According to the present invention, there is provided a mobile network system comprising a mobility management node and a circuit-switched node. If the mobility management node restart is performed, the circuit-switched node sends to the mobility management node a notification message including the identification information associated with the mobile station and the location registration area information. The management node performs locating by including identification information associated with the mobile station to an area corresponding to the location registration area information.
[0028] In accordance with the present invention, a node apparatus is provided which manages a bearer, whereby the node apparatus maintains a specific eligible bearer for the re-establishment of communication services, and removes other bearers. In case the mobility management node restart is performed, the node appliance keeps at least one of the bearers as defined. Effect of the invention
[0029] According to the present invention, it is possible to accelerate the restoration of a communication service to a mobile station following the restart of a mobility management node. Brief description of the drawings
[0030] Figure 1 is a diagram to illustrate the operation of a mode of the present invention;
[0031] Figure 2 is another diagram to illustrate the operation of the mode of the present invention;
[0032] Figure 3 is yet another diagram to illustrate the operation of the mode of the present invention;
[0033] Figure 4 is yet another diagram to illustrate the operation of the mode of the present invention;
[0034] Fig. 5 is yet another diagram to illustrate the operation of the mode of the present invention;
[0035] Figure 6 is a diagram to illustrate a packet communication network that accommodates LTE;
[0036] Figure 7 is a diagram to illustrate a packet communication network that accommodates 2G/3G;
[0037] Figure 8 is a diagram to illustrate a packet communication network that accommodates LTE and 2G/3G;
[0038] Figure 9 is a diagram to illustrate CSFB (Circuit Switching Backward);
[0039] Fig. 10 is a diagram for illustrating an example sequence of an exemplary configuration 1 of the present invention;
[0040] Fig. 11 is a diagram to illustrate another example sequence of the exemplary configuration of the present invention;
[0041] Fig. 12 is a diagram to illustrate yet another example sequence of exemplary configuration 1 of the present invention;
[0042] Fig. 13 is a diagram for illustrating an exemplary operational sequence of an exemplary configuration 2 of the present invention;
[0043] Fig. 14 is a diagram to illustrate another exemplary operational sequence of exemplary configuration 2 of the present invention;
[0044] Fig. 15 is a diagram to illustrate yet another exemplary operational sequence of exemplary configuration 2 of the present invention;
[0045] Fig. 16 is a diagram for illustrating an example operational sequence of an exemplary configuration 3 of the present invention;
[0046] Fig. 17 is a diagram to illustrate another exemplary operational sequence of exemplary configuration 3 of the present invention;
[0047] Fig. 18 is a diagram for illustrating an example operational sequence of an exemplary configuration 4 of the present invention;
[0048] Fig. 19 is a diagram to illustrate another exemplary operational sequence of exemplary configuration 4 of the present invention;
[0049] Fig. 20 is a diagram to illustrate yet another exemplary operational sequence of exemplary configuration 4 of the present invention;
[0050] Fig. 21 is a diagram to illustrate an example operational sequence of an exemplary configuration 5 of the present invention;
[0051] Fig. 22 is a diagram to illustrate another exemplary operational sequence of exemplary configuration 5 of the present invention;
[0052] Fig. 23 is a diagram to illustrate yet another exemplary operational sequence of exemplary configuration 5 of the present invention; and
[0053] Fig. 24 is a diagram to illustrate an example operational sequence of a mode of the present invention. Preferred modes for carrying out the invention
[0054] In one of the preferred modes of the present invention, when a mobility management node, such as MME/SGSN, has restarted, an S-GW bearer management node does not release all relevant bearers to the mobility management node. MME/SGSN. The bearer management node (S-GW) retains at least part of all bearers to continue a packet reception service. That is, when the bearer management node such as S-GW detects the restart of the mobility management node (MME/SGSN), the bearer management node confirms that the mobile station UE is accommodated in the management node of the bearer. mobility (MME/SGSN). In connection with the mobile station (UE), accommodated in the mobility management node (MME/SGSN), the bearer management node such as S-GW holds at least one of the bearers defined in a direction of the management node of bearers (S-GW) towards the external network, such as PDN. By doing this, the mobile station (UE) is able to attach itself to the network, with packets received from the external network (PDN) to the mobile station (UE) as a trigger, thus accelerating the re-establishment of a communication service for the mobile station (UE). In one of the preferred modes of the present invention, the bearer management node maintains a specific bearer(s) to re-establish a communication service, and removes other bearers. In one of the preferred modes of the present invention, when holding the specific bearer, the bearer management node can start a timer. When the timer times out, the bearer management node can remove bearer resources that have been held.
[0055] In one of the preferred modes of the present invention, it is possible to select those bearers that provide high reliability services after the restart of the mobility management node (MME/SGSN). It is therefore possible to suppress the resource consumption of the bearer management node (S-GW) as well as avoid congestion due to the concentration of location records.
[0056] In one of the preferred modes of the present invention, the S-GW bearer management node maintains the location registration area information (TA/RAI List) of the mobile station (UE), reported from the management node (MME/SGSN), and the identification information (IMSI) associated with the mobile station. After the restart of the mobility management node (MME/SGSN), the bearer management node (S-GW) can, with data reception arriving at the mobile station (UE), notify the registration area information of location (TA/RAI list) and identification information (IMSI) for the mobility management node (MME/SGSN). The Mobility Management Node (MME/SGSN) can then perform location, using the identification information (IMSI), for only the area corresponding to the location registration area information (TA/RAI List). By doing so, it is possible to selectively reduce an area that is located by the base station.
[0057] Figure 1 is a diagram to illustrate one of the modes of the present invention. A mobility management node (MME/SGSN) that manages registration information of a mobile station UE, notifies the registration information of the mobile station UE's location to an S-GW at the beginning. The S-GW maintains the UE mobile station location log information. The S-GW also maintains carriers between the S-GW and the P-GW.
[0058] Restart takes place on MME/SGSN Mobility Management Node.
[0059] When the S-GW detects, e.g. health check, that the MME/SGSN mobility management node has restarted, the S-GW does not release but maintains bearers that are defined between the S-GW and the P-GW. In this case, in view of the compatibility of stable system restoration and availability of communication services, it is possible for the S-GW not to release but to continue to maintain those bearers that will provide high availability services. These services can be exemplified by communication that is requiring high reliability according to, eg, operator policy, such as voice services provided by IMS. For example, the S-GW may not release but maintain specific S5/S8 bearers between the S-GW and P-GW that are required for re-establishing services initiated from the network side, and remove all other S5/S bearers. S8.
[0060] In an example shown in figure 2, when the S-GW detects e.g. health check (eco-GTP) that the mobility management node MME/SGSN has restarted, the S-GW releases IMS control bearer services, between defined bearers between the S-GW and the P-GW, maintaining only the bearers used for IMS control. By thus only applying to specific services, it is also possible to gradually restore the MME/SGSN while system-wide overload is avoided.
[0061] Figure 3 is a diagram to illustrate the case of applying the present invention to IMS services. When packet data has arrived, using the bearer maintained by the S-GW, the arriving packet is notified, along with the IMSI ID for the UE and the location registration area information, recorded in advance on the S-GW, to the MME /SGSN where the restart took place. The MME/SGSN is therefore able to call 1 (locate) the UE using the IMSI and location registration area information. The mobile station UE that was located using the IMSI, performs re-registration (append) to the MME/SGSN and re-establishes the bearers necessary to receive full packet communication services. Thus, according to a mode of the present invention, even if the MME/SGSN restarts, the service arrival can be notified to the mobile station UE to induce its attachment to the MME to improve the availability of communication services.
[0062] According to one mode of the present invention, it is possible to make the UE attach itself to the network after the MME/SGSN restart, with the reception of the packet to the UE as a trigger. Packet communication services can be instantly restored to the UE whose services were started by the arrival of the received packet.
[0063] In one mode of the present invention, only those carriers that need high reliability can be taken as carriers to be maintained in accordance with the present invention. It is therefore possible to suppress the consumption of S-GW resources as well as congestion due to the concentration of location records. This operation is indispensable especially if a UE where communication occurs periodically, as in MTC, is accommodated. The reason is that, in such a case, packet communication occurs for many UEs after MME/SGSN restart, and therefore subscriber recovery operations can occur in a bursty fashion, with packet communication as a trigger. , thus possibly leading to system congestion as a whole.
[0064] Figs. 4 and 5 are diagrams showing an example in which the present invention is applied to CSFB. The CSFB function switches voice origination/arrival to 3G to produce voice services employing the 3G-CS domain even in case VoIP services are not provided on LTE. Regarding the CSFB function, reference is made to Non-Patent Document 3 (figure 7.2.1 Mobile Termination Call in idle mode).
[0065] Referring to Figure 4, MME notifies UE location registration information to an MSC in advance. When MME restarts, MSC detects MME restart eg. a health check. Referring to Figure 5, when a call has arrived from a G-MSC (Incoming CS) from the origination side, the MSC notifies the IMSI and the location registration area to the MME, which MME is able to call ( locate) the UE using the IMSI and location registration area information.
[0066] The following describes exemplary embodiments of the present invention. Figs. 6 to 9 show networks to which the present invention can be applied. <Example Configuration 1>
[0067] Figure 6 is a diagram showing a network configuration of an exemplary configuration 1 of the present invention. Specifically, Figure 6 shows a packet communication network that accommodates LTE. Referring to Figure 6, the network includes a mobile station (UE) 101, a base station (e-NodeB) 102, an MME 103, an HSS 106, an S-GW 104, a P-GW 105, a network (PDN) 108 and an IMS 109. The IMS 109 is a communication system that integrates packet-switched communication services over SIP (Session Initiation Protocol) to implement multimedia services.
[0068] MME 103 accommodates e-NodeB 102 through an S1-MME interface to perform UE mobility management and authentication as well as defining a user transmission path. MME 103 refers to HSS 106 which is a database for managing subscriber information through an S6a interface to perform eg authentication. The MME 103 transmits/receives a control signal via the S1-MME and S11 interfaces to prepare or release the user's transmission path on an S1-U interface between the e-NodeB and the S-GW. The transport protocol on the S1-U interface between e-NodeB and S-GW is GTP-U.
[0069] An S5/S8 interface 107 is an interface (user plane) between S-GW and P-GW. As a transport protocol, a tunnel protocol (GTP-U) or a Proxy Mobile IP protocol (P-MIP), is defined.
[0070] The S-GW 104 performs transmission/reception of user data between itself and the e-NodeB 102, while preparing or releasing an external PDN-based transmission path via the P-GW and S5/S8 interface 107. The P -GW 105 connects to the external network (PDN) 108 through an SGi interface. The following describes an operation when the MME restarts. <First stage>
[0071] Fig. 10 is a sequence diagram illustrating, as a first stage, a stage for recording location registration area information of the mobile station UE in the S-GW. In figure 10, the base station (e-NodeB) 102 of figure 6 is omitted. It is assumed that the mobile station UE1 has set up a radio control link between itself and the e-NodeB. The respective steps of figure 10 will now be described.
[0072] In a step 1 of figure 10, the mobile station UE1 transmits a location registration request (Append Request or TAU Request) to the MME1. Note that, in LTE, the location of the mobile station UE in an idle (ready) mode is managed by location registration area (tracking area) information. Each tracking area corresponds to a location area or a routing area in 3G/UMTS, and is composed of one or a plurality of cells. In each of these cells, an identifier of the tracking area to which the cell in question belongs is transmitted. The mobile station in an idle mode has its location recorded in the tracking area in which the mobile station UE resides, and stores the identifier of the tracking area in which the UE currently has its location recorded. When moving from one cell to another, the mobile station UE receives the tracking area identifier which is transmitted. If the tracking area identifier being transmitted differs from the tracking area identifier currently registered in it, the UE updates the location record. A request to update this location record is called a 'TAU Request'.
[0073] In a step S2 of Fig. 10, the MME1 again assigns the location registration area information (TA List) to the mobile station UE1.
[0074] In a step S3 of figure 10, the MME1 informs the S-GW1 about the TA list of the mobile station UE1 via the S11 interface. The S-GW1 stores the TA List, reported by the MME1, in a storage unit (memory) in the S-GW1, as the registration information of the mobile station UE1. It is noted that the location recording operation in steps 1 and 2 of Fig. 10 is known PER SE and is not directly relevant to the subject matter of the present invention. Therefore, the operation is not explained in detail. <Second stage>
[0075] Figure 11 is a sequence diagram to illustrate, as a second stage, the maintenance stage of a carrier. In a step 1 of Fig. 11, the mobile station UE1 has already attached itself to the MME1 (an attachment request has already been issued). A variety of carriers have already been prepared using S-GW1 and P-GW1.
[0076] In step 2 of figure 11, the restart of MME1 occurs and in this MME1, the registration information of UE1, already attached, is deleted.
[0077] In step 3 of figure 11, the S-GW1 detects the restart of MME1, from processing such as a health check by Echo GTP processing.
[0078] In a step 4 of figure 11, the S-GW1 recognizes all the mobile stations UEs attached to the MME1 (it is confirmed that the UE1 is accommodated in the MME1).
[0079] If the present invention is provided for all services, all bearers related to the mobile station UE1 from the S-GW1 towards the external network IMS 1 are kept in step S5 of figure 11.
[0080] In steps 6 and 7 of figure 11, a distinction from step S5 of figure 11, the bearer maintenance function according to the present invention is not provided for all services related to mobile station UE1, such that bearers (bearers used for IMS control) are held for specific services (IMS services providing eg voice services).
[0081] After confirming in step S4 of figure 11 that the mobile station UE1 was accommodated in MME1, the S-GW1 additionally confirms, in step 6 of figure 11, whether or not there is a bearer(s) providing the IMS (bearer( es) used for IMS control) between the bearers owned by the mobile station UE1. When verifying the bearers used for IMS control in this way, a QCI (QoS Class Identifier) value, which is among the information elements that each bearer has, can be used. If, when using the QCI value, it is '5', for example, the bearer can be concluded to be the bearer(s) used for IMS (IMS Signaling) control, according to Table 6.1.7 of Non-Patent Document 1 (3GPP TS23.03). The bearer can then be concluded to be a control bearer used to provide voice services.
[0082] If the bearer(s) used for IMS control exist among bearers related to the mobile station UE1 managed by the S-GW1, only the relevant bearer(s) es) is (are) maintained. The remaining carriers are locally released in accordance with the transaction in accordance with Non-Patent Document 2 (3GPP TS23.007).
[0083] In case of maintenance of carriers used for IMS control (specific carriers), the S-GW1 starts the operation of a timer to release (remove) relevant carrier resources upon time-out, in consideration of a case where the mobile station UE1 has already reattached to another S-GW. This timer controls a specific bearer hold time mentioned above by the S-GW1, and becomes necessary to prevent failure to release the bearers that the S-GW1 holds. If, in the above timer, the time equivalent to the time of a periodic location record timer possessed by the mobile station UE1 is set, the S-GW1 can wait for the arrival of voice services for a required minimum time interval corresponding to the time in the next periodic location registration request from UE1. At this time, the fact that the mobile station UE1 was not registered in the MME1 is stored in the storage unit (memory) of the S-GW1.
[0084] In a step 7 of figure 11, the mobile station UE1 is not registered in the MME1 and only the IMSI control bearer is kept in the S-GW1 and the P-GW1. This completes the second stage.
[0085] If the third stage, shown in figure 12 has not been performed after this, the S-GW1 removes all of the bearers (IMS control bearer resources) that the S-GW1 maintains in connection with the mobile station UE1 , when the timer whose operation was started in step S6 of figure 11 has expired. <Third stage>
[0086] Figure 12 is a sequence diagram showing the operation of a third stage if a signal has reached the second stage from the PDN such as IMS. The following describes the respective stages.
[0087] In a step 1 of figure 12, a notification from the IMSI, indicating the arrival of voice services for the mobile station UE1, arrives at the G-SW1.
[0088] In a step S2 of figure 12, the G-SW1 stores the information that the station UE1 is in an unregistered state due to the restart of the MME1. Therefore, the G-SW1 sends a downlink data notification (Downstream Data Notification), including the IMSI and the previously registered TA List, to the MME1 to inform the arrival.
[0089] If, in a step S3 of Fig. 12, the mobile station UE1, having the IMSI that was notified, is not attached, the MME1 performs the location of the mobile station UE1 for the received TA List, using the IMSI. However, there is such a case where, when executing step S3, the mobile station UE1 has already selected another S-GW and attached itself to MME1. In this case, to induce the S-GW1 to release all relevant bearers to the mobile station UE1, the MME1 returns a downstream data notification acknowledgment response (Downstream Data Notification Acknowledgment) indicating the cause that UE1 has already annexed.
[0090] In a step 4 of figure 12, the mobile station UE1 performs the attachment operation with the location reception using the IMSI.
[0091] The operation of attaching the mobile station UE1 in step 4 of figure 12 is well known to those skilled in the art and not directly relevant to the present invention. Therefore, the detailed configuration explanation is dispensed with.
[0092] When S-GW detects MME restart, if tunnel (GTP-U) on S1-U interface between e-NodeB and S-GW is active, S-GW releases tunnel. <Example configuration 2>
[0093] As an exemplary configuration 2 of the present invention, the following describes the operation at the time of the SGSN restart in the network configuration of figure 7. Basically, the operation of the exemplary configuration 2 is equivalent to the operation at the time of the MME restart in the configuration exemplar 1. In the example of figure 7, 2G/3G is accommodated. Specifically, the e-NodeB 102 and MME 103 of Figure 6 are replaced by a 2G/3G radio control apparatus (B and RNC node) 110 and an SGSN 111. An interface between the 2G/3G radio control apparatus ( NodeB and RNC) 110 and SGSN 111 is Iu, an interface between 2G/3G radio control apparatus (NodeB and RNC) 110 and S-GW 104 is S12, an interface between SGSN and S-GW is S4 and an interface between the SGSN 111 and the HSS 106 is an S6d/Gr.
[0094] The operation of this exemplary configuration can be summarized to have three separate stages. <First stage>
[0095] Fig. 13 is a sequence diagram showing a stage for recording the location registration area information of the mobile station UE in the S-GW1, as a first stage. The following describes the respective steps.
[0096] In a step S1 of figure 13, the mobile station UE1 sends a location registration request (Attachment Request/Routing Area Update Request) to SGSN1. The Routing Area Update Request is a location record update request for the SGSN.
[0097] In a step S2 of Fig. 13, the SGSN1 again assigns the location registration area information (RAI) to the mobile station UE1.
[0098] In a step 3 of figure 12, the SGSN1 notifies the S-GW1 about the RAI of the mobile station UE1. The S-GW1 keeps the RAI notified of the registration information of the mobile station UE1.
[0099] The location recording operation of Figure 12 is known PER SE among those skilled in the art and is not directly relevant to the subject matter of the present invention. Therefore, the configuration is not explained in detail. <Second stage>
[0100] Figure 14 is a sequence diagram for the maintenance stage of a carrier, as a second stage. The following describes the respective steps.
[0101] In a step S1 of figure 14, mobile station UE1 has already been attached to SGSN1, and various types of bearers have been prepared using S-GW1 and P-GW1.
[0102] In step 2 of figure 14, the restart process takes place in SGSN1. The registration information of the attached mobile station UE1 is deleted.
[0103] In step 3 of figure 14, the S-GW1 detects the restart in SGSN1 by processing, such as a health check, by GTP Echo processing.
[0104] In a step S4 of figure 14, the S-GW1 recognizes all the mobile stations UE (it is confirmed that the mobile station UE1 is accommodated in SGSN1).
[0105] If the present invention is applied to all services, all carriers are kept in step 5 of figure 14.
[0106] In steps 6 and 7 of figure 14, bearers are not maintained for all services, as is done in step 5 of figure 11. On the contrary, only a bearer related to a specific service (IMS service, providing p .e.g. voice services in the following example) is maintained.
[0107] After step S4 of figure 14 to confirm that the mobile station UE1 is accommodated in SGSN1, the S-GW1 confirms, in a step 6 of figure 14, whether or not the IMS signaling bearer exists among the bearers maintained by the mobile station UE1. The IMS signaling bearer is a bearer used for IMS control, the QCI (QoS Class Identifier) value, which is one of the control elements possessed by each bearer, for example, can be used. If the QoS value is '5', for example, a bearer in question is determined to be the IMS control bearer (IMS signaling) in accordance with Table 6.1.7 of Non-Patent Document 1 (3GPP TS 23.203). The bearer in question can therefore be determined to be a control bearer used to provide voice services. If such an IMS control bearer exists, the S-GW1 maintains only that bearer, and locally releases (removes) other bearers in accordance with the operation of Non-Patent Document 1 (3GPP TS23.007).
[0108] If the IMS control bearer is maintained, the operation of a timer, which at the end of the time releases the bearer, is initiated to take into account the case where the mobile station UE1 has already connected to another S-GW1. This timer is necessary to prevent failure to release carriers that the S-GW1 holds.
[0109] If, in the above timer, the time equivalent to the time of a periodic location record timer included in the mobile station UE1 is set, the S-GW1 can wait for the arrival of voice services for a minimum necessary time corresponding to the time of the next periodic location registration request from UE1. At this time, the fact that mobile station UE1 was not registered in SGSN1 is stored in S-GW1.
[0110] In a step S7 of figure 14, SGSN1 is in a state such that mobile station UE1 has not been registered and that only the IMS control bearer is kept in S-GW1 and P-GW1.
[0111] If after that the third stage shown in figure 15 is not executed, the S-GW1 removes all the bearers held in connection with the mobile station UE1 (IMS control bearer resources) at a timeout point of the timer whose operation started in step 6 of figure 14. <Third stage>
[0112] Figure 15 is a sequence diagram to illustrate the operation of a third stage in the case of an arrival from the PDN, such as IMS.
[0113] In a step S1 of figure 15, the notification of the arrival of voice services from the IMSI to the mobile station UE1 arrives at the S-GW1.
[0114] In a step S2 of figure 15, the S-GW1 sends the IMSI and downlink data notification (Downlink Data Notification) inclusive of IMSI and RAI that have been registered in advance to the MME to inform the arrival . It is because S-GW1 stores that mobile station UE1 is in an unregistered state because of SGSN1 reset.
[0115] If the mobile station UE1 that had the notified IMSI was not attached, the SGSN1 in a step S3 in figure 15 performs the location of the mobile station UE1, for the received RAI, using the IMSI. However, there is such a case where, when executing step S3 of Fig. 15, the mobile station UE1 has already selected another S-GW and attached itself to SGSN1. In this case, to induce the S-GW1 to release all relevant bearers to the mobile station UE1, the SGSN1 sends back to the S-GW1 a downstream data notification acknowledgment response (Downstream Data Notification Acknowledgment) indicating the cause because UE1 had already annexed itself.
[0116] In a step 4 of figure 15, the mobile station UE1 that had received the location employing the IMSI performs an attach operation. The operation of attaching the mobile station UE of step S4 of Fig. 15 is known PER SE among those skilled in the art and is not directly relevant to the subject matter of the present invention. Therefore, its detailed configuration is omitted. <Example configuration 3>
[0117] As an exemplary configuration 3 of the present invention, the following describes the operation in case of employing an ISR function (LTE/3G location record omission function) under the network configuration of figure 8. In ISR, the station Mobile UE records its location in both the MME and the SGSN. In a case of switching a radio access system between LTE and 2G/3G, the UE location registration is omitted as long as there is no change in the location area previously registered in LTE and that in 2G/3G. Figure 8 shows a packet communication network configuration accommodating LTE and 2G/3G. This configuration corresponds to the configuration of the added figure 1 of a 2G/3G radio control apparatus 110 and an SGSN 111 to be connected to the mobile station UE 101. The MME 103 is connected to the SGSN 111 via an S3 interface, while the MME 103 and the SGSN 111 are connected to the HSS 106 via an S6 interface and an S6d/Gr interface. The S-GW 104 is connected to the SGSN 111 and the MME 103 via an S4 interface and via an S11 interface. <First stage>
[0118] Location registration processing for UE1 from 2G/3G, as a first stage, is shown in figure 13. Figure 10 can apply as it relates to location registration processing from LTE. By these two operations, the S-GW1 maintains RAI and TA List as the location registration area information. The processing of the location record during ISR operation is known PER SE among those skilled in the art and is not directly relevant to the subject matter of the present invention. Therefore, its detailed configuration is omitted. <Second stage>
[0119] Figure 16 is an example of a sequence as an operation in case of restart of MME1 of figure 8. Figure 17 shows an example of a sequence as an operation in case of restart of SGSN1 of figure 8.
[0120] In a step S1 of figure 16, the mobile station UE1 has its location registered in the MME1, and various types of bearers that have been established using the S-GW1 and the P-GW1.
[0121] In a step 2 of figure 16, the restart takes place in the MME1, such that the registration information of the mobile station UE1 in the MME1 is erased.
[0122] In step 3 of figure 16, the S-GW1 detects the restart of MME1 from processing, such as a health check by Echo GTP processing.
[0123] In a step 4 of figure 16, the S-GW1 does not perform bearer release because the S-GW1 knows that the mobile station UE1 attached to the MME1 has been registered using the SGSN1 and the ISR function. At this time, the fact that the mobile station UE1 is not registered in the MME1 is stored in an internal memory of the S-GW1. However, if the SGSN1 had already been restarted, the processing according to the present invention (carrier maintenance processing relevant to the mobile station UE1) is performed as in the processing of Fig. 11.
[0124] The following describes the operation if the SGSN1 in figure 8 had restarted.
[0125] In a step 1 of figure 17, the mobile station UE1 has its location registered in SGSN1, and several types of bearers have already been prepared using the S-GW1 and the P-GW1.
[0126] In a step 3 of figure 17, the restart processing, for example, takes place in SGSN1, and the registration information of the mobile station UE1, which had its location registered, is deleted.
[0127] In step 3 of figure 17, the S-GW1 detects the restart of SGSN1 from processing such as a health check by Echo GTP processing.
[0128] In a step 4 of figure 17, the S-GW1 does not perform bearer release because the S-GW1 knows that the mobile station UE1 attached to the MME1 has been registered using the MME1 and the ISR function. The unregistered status of mobile station UE1 in SGSN1 is stored in the internal memory of S-GW1. However, if the MME1 has already restarted, the processing according to the present invention (processing for maintenance of the bearer relevant to the mobile station UE1) is performed as with the processing of Fig. 14. <Third stage>
[0129] Figure 18 is a diagram showing an example of an operation sequence if there is an arrival from the PDN under a condition that the MME1 of Figure 8 has restarted, as a third stage. Fig. 19 is a diagram showing an example of an operation sequence if there is an arrival from the PDN under a condition that the SGSN1 of Fig. 8 is reset. Fig. 20 is a diagram showing an example of an operation sequence if there is an arrival from the PDN under a condition that both MME1 and SGSN1 of Fig. 8 are reset.
[0130] If there is an arrival from the PDN under a condition that the MME1 of figure 8 is restarted, the notification of arrival of communication services from the PDN1 to the mobile station UE1 arrives at the S-GW1 in a step 1 of the figure 18.
[0131] In a step 2 of figure 18, the S-GW1 sends a normal downstream data notification (Downstream Data Notification) to the SGSN1 to inform the arrival.
[0132] In a step 3 of figure 18, the S-GW1 sends a downstream data notification (Downstream Data Notification), inclusive of the IMSI and the pre-registered TA List, to the MME1 to inform the arrival. It is because S-GW1 stores the unregistered state of mobile station UE1 on account of MME1 restart.
[0133] In a step 4 of figure 18, SGSN1 performs normal localization (location of mobile station responsive on arrival).
[0134] In a step 5 of figure 18, if the mobile station UE1 having the IMSI according to the notification is not attached, the MME1 performs the location of the mobile station UE1, using the IMSI, referring to the received TA List.
[0135] In a step 6 of figure 18, the location employing the IMSI is received in LTE, the mobile station UE1 performs an attach operation.
[0136] The following describes a case where an arrival from the PDN is performed under a condition that the SGSN has restarted.
[0137] In a step 1 of figure 19, the notification of arrival of communication services from PDN1 to mobile station UE1 arrives at S-GW1.
[0138] In a step 2 of figure 19, the S-GW1 sends normal downstream data notification (Downstream Data Notification) to the MME1 to inform the arrival.
[0139] In a step 3 of figure 19, the S-GW1 sends a downstream data notification (Downstream Data Notification), including the IMSI and the pre-registered RAI, to the SGSN1 to inform the arrival. It is because S-GW1 stores the unregistered state of mobile station UE1 on account of MME1 restart.
[0140] In step 4 of figure 18, SGNS1 performs normal localization.
[0141] In a step 5 of figure 18, if the mobile station UE1 having the IMSI according to the notification was not attached, the SGSN1 performs the location of the mobile station UE1, using the IMSI, referring to the received RAI.
[0142] In a step 6 of figure 19, if the location using the IMSI is received in 2G/3G, the mobile station UE1 performs an attachment operation.
[0143] The following describes a case where an arrival from the PDN is performed under a condition that both the MME and SGSN have been reset.
[0144] In a step 1 of figure 20, the notification of arrival of communication services from PDN1 to mobile station UE1 arrives at S-GW1.
[0145] In a step 2 of figure 20, the S-GW1 sends a downstream data notification (Downstream Data Notification), inclusive of the IMSI and the pre-registered TA List, to the MME1 to inform the arrival. It is because S-GW1 stores the unregistered state of mobile station UE1 on account of MME1 restart.
[0146] In step 3 of figure 20, the S-GW1 sends a downstream data notification, including the IMSI and the pre-registered TA List, to the SGSN1 to inform the arrival. It is because S-GW1 stores the unregistered state of mobile station UE1 which is due to restart of MME1.
[0147] In a step 4 of figure 20, if the mobile station UE1 having the IMSI according to the notification is not attached, the MME1 performs the location of the mobile station UE1, using the IMSI, referring to the received TA List.
[0148] In a step 5 of figure 20, if the mobile station UE1 having the IMSI according to the notification is not attached, the SGSN1 performs the location of the mobile station UE1, using the IMSI, referring to the received RAI.
[0149] In a step 6 of figure 20, when receiving the location using the IMSI, the mobile station UE1 performs an attach operation.
[0150] The mobile station UE attachment operation of step S6 of figs. 11, 12 and 13 is known PER SE among those skilled in the art and is not directly relevant to the subject matter of the present invention. Therefore, the detailed configuration is omitted. <Example configuration 4>
[0151] Figure 9 is a diagram showing a network configuration in accordance with a fourth exemplary configuration in accordance with the present invention. Figure 9 shows a CSFB (CS Backtrack) architecture. Referring to Figure 9, the network includes the mobile station (UE) 101, a base station (e-NodeB) 102, an MME 103, an HSS 106, an MSC/VLR 112, a CS network 113 and a G- MSC (Gateway Mobile Exchange) 114. The following describes the incoming voice operation from the G-MSC 114 as an origination source to the mobile station (UE) 101 with reference to Fig. 9.
[0152] A signal notifying the arrival is sent from the G-MSC 114 as an origination source to the MSC/VLR 112 via the CS network 113. The MSC/VLR 112 identifies the corresponding MME 103 from the arrival information to send a location request message (Location Request Message) to the MME 103. The MME 103 sends a location signal to mobile stations residing in the service area. This location signal includes information indicating that the location is for CS services. The mobile station UE 101 recognizes this information, i.e. the information that the location is that for CS services, and sends a CS service request signal to the MME 103. The MME sends a frequency transfer command to the UE1. Mobile station (UE) 101 performs frequency transfer while switching to 3G. The mobile station UE 101, which has switched to 3G, sends a location response to the MSC/VLR 112, as a result of which the voice services at the mobile station for the incoming voice are initiated. The following describes the operation when the MME restarts.
[0153] The operation according to the present invention can be summarized to have three separate stages. <First stage>
[0154] Fig. 21 is a sequence diagram showing, as a first stage, the stage for recording location registration area information of the mobile station UE. The following describes the respective steps.
[0155] In a step 1 of figure 21, the mobile station UE1 makes a location registration request for CSFB (Append Request, TAU Request and so on) to the MME1.
[0156] In a step 2 of figure 21, the MME1 again assigns (provides) the location registration area information (TA List) to the mobile station UE1.
[0157] In a step 3 of figure 21, MME1 notifies MSC1 of the TAU List of mobile station UE1. MSC1 maintains the TAU List notified from MME1, as the registration information of mobile station UE1.
[0158] The location recording operation of Figure 21 is known PER SE among those skilled in the art and is not directly relevant to the subject matter of the present invention. Therefore, the detailed configuration is omitted. <Second stage>
[0159] Figure 22 is a sequence diagram showing, as a second stage, the maintenance stage of a carrier. The following describes the respective steps.
[0160] In a step 1 of figure 22, the mobile station UE1 has already attached itself to the MME1.
[0161] In a step 2 of figure 22, the restart takes place in the MME1 and the registration information of the mobile station UE1 is erased.
[0162] In step 3 of figure 22, MSC1 detects the restart of MME1 from processing such as a health check by SCTP.
[0163] In a step 4 of figure 22, the MSC1 recognizes all the mobile stations UE attached to the MME1 (it is recognized that the mobile station UE1 is accommodated in MME1). The above is the second stage. <Third stage>
[0164] Figure 23 represents an exemplary sequence diagram showing, as a third stage, a sequence of operations for the arrival case (voice arrival, or SMS, for example) via a CS domain. The following describes the respective steps.
[0165] In a step 1 of figure 23, an arrival notification for the mobile station UE1 arrives at the MSC1 by, eg, the G-MSC.
[0166] In step 2 of figure 23, MSC1 sends a location request message inclusive of the IMSI and pre-registered TA List (REQUEST-LOCATION-SGsAP message) to MME1 to notify MME1 of arrival. It is because MSC1 stores the unregistered state of mobile station UE1 produced by restarting MME1.
[0167] In a step 3 of figure 23, if UE1 having the IMSI notified to it has not attached itself, the MME1 performs a location of the mobile station UE1, using the IMSI, for the received TA List.
[0168] However, there is such a case where, when executing step S3 of figure 23, the mobile station UE1 has already selected another MSC and attached itself to MME1.
[0169] In this case, to induce MSC1 to release all relevant carriers for mobile station UE1, MME1 sends back to MSC1 a location rejection message (REJECTION-LOCATION-SGsAP message) indicating the cause why the UE1 had already attached itself.
[0170] In a step 4 of figure 23, the mobile station UE1, which had received the location using the IMSI, performs an attach operation. The operation of attaching the mobile station UE in step 4 of Fig. 23 is known PER SE among those skilled in the art and is not directly relevant to the subject matter of the present invention. Therefore, the configuration is omitted.
[0171] In the drawings of the exemplary configuration described above, only one (P-GW1) is shown as the P-GW for simplicity of explanation. However, a plurality of P-GWs, such as P-GW2, P-GW3 or P-GWN, can be used in a similar manner.
[0172] Another of the modes of the present invention will now be explained with reference to Fig. 24, which supplements Fig. 10, for example, and shows the resetting of subscriber data per service request triggered by the network. It is noted that the e-NodeB is omitted in figure 24.
[0173] S1) The MME sends the latest TA List to a relevant S-GW. That is, the MME reports the latest TA List on a per UE basis to one or more S-GWs at each occurrence of mobility events. This information (TA List) is important in case of MME failure because locating the IMSI for MME coverage in its entirety can be avoided in this way. Since larger numbers of e-NodesB are accommodated in an MME, the load on the EPS system can become tremendously severe if localization has to be performed for all coverage.
[0174] S2) MME performs restart.
[0175] S3) With a reset counter increased by one, a TTP Echo message (GTP-V2 Echo Reply Message) is sent to all relevant S-GWs.
[0176] S4) The relevant S-GW detects MME failure by this GTP echo mechanism. The S-GW is capable of maintaining all or selected carriers, IMSI and the TA List. An operator is able to select a carrier based on top ranking services (IMS) (top service (IMS)), as a result of which carrier held can be selected only for important services. For other (selected) carriers, the current MME reset mechanism is applied. If the S-GW has to maintain the bearer resources, IMSI and the TA List, the S-GW starts a timer that controls a time interval to maintain the bearer resources, for example. On timer exhaustion, held bearer resources are removed. This alternative is necessary for such a case in which, when the UE re-attaches to a network, the S-GW in question is not selected. That is, on timer running out of the S-GW in question, the aforementioned carrier resources held, for example S5/S8 carriers, which are specific held carriers, are removed in the event that the UE has reattached itself to the network via an S -GW different from the S-GW in question.
[0177] S5) DL data arrives at the P-GW from an external network (PDN).
[0178] S6) The S-GW acquires the DL data from the P-GW.
[0179] S7) The S-GW sends a downstream data notification message inclusive of the IMSI and TA List (DL Data Notification (IMSI, TA List)) to the MME.
[0180] S8) MME starts IMSI find ((Find (IMSI) for specific TAs in TA List) for all TAs in TA List received from S-GW.
[0181] S9) Upon receiving the IMSI location, the mobile station UE1 starts the attachment procedure (ATTACH).
[0182] S10) Upon receiving the attachment request (ATTACH) from the UE, the MME sends a location information update request to the HSS.
[0183] S11) HSS sends location information update confirmation to MME.
[0184] S12) MME sends APPEND acceptance to mobile station UE via e-NodeB.
[0185] In case of detecting MME restart, S-GW keeps bearer, IMSI or TA List. In this way, it is possible to instantly recover communication services after restarting the MME and after the arrival of the DL data in the UE from the PDN side.
[0186] In a mode of the present invention, if only selected carriers are to be kept, it is possible to suppress the resource consumption of the S-GW. In addition, by selecting and maintaining bearers for important services, communication services can be instantly re-established to higher-ranking services after MME restarts.
[0187] In another mode of the present invention, if a bearer is to be maintained by itself or together with the IMSI and the TA List, the maintenance time interval is managed by a timer. On timer exhaustion, the held bearer, IMSI and TA list are released. By doing so, if, after the MME restart, the mobile station moves and attaches to a different G-SW than the S-GW holding the bearer, it is possible to prevent the S-GW holding the bearer from holding the bearer longer. than necessary.
[0188] According to the present invention, described above, the following effects can be realized.
[0189] UE communication services can be improved in availability by adding packet arrival with a re-registration trigger of a UE registered in the MME/SGSN on which the restart took place.
[0190] If the present invention is applied to all services, the arrival of all packets can be used as a trigger to restore the UE to the network. It can be imagined, however, that many resources on the S-GW side are used, and that location log events can be concentrated. The S-GW1 is able to maintain the TA List and perform localization processing using the TA List. However, if it is not possible for the S-GW to receive the TA List from the MME1, the location can be performed for the entire area supervised by the MME1. In this case, many of the resources on the radio network side would be consumed.
[0191] In accordance with the present invention, the S-GW1 is able to maintain the RAI and perform location processing using the RAI. If it is not possible for the S-GW1 to receive the RAI from SGSN1, the location can be performed for the total areas supervised by the SGSN. In this case, many of the resources on the radio network side would be consumed.
[0192] The disclosures of the aforementioned Non-Patent Documents are hereby incorporated by reference. Particular exemplary configurations or examples may be modified or adjusted within the range of the full disclosure of the present invention, including the claims, based on the fundamental technical concept of the invention. Additionally, various types of combinations or selection of elements disclosed herein can be made within the framework of the claims. That is, the present invention can cover a wide variety of modifications or corrections that may occur to those skilled in the art in accordance with the full disclosure of the present invention, including the claim and the technical concept of the present invention. Explanation of symbols 101 UE 102 e-NodeB 103 MME 104 S-GW 105 P-GW 106 HSS 107 S5/S8 108 external network 109 IMS 110 2G/3G radio control device (NodeB/RNC) 111 SGSN 112 MSC/VLR 113 CS 114 G-MSC network (mobile door switching center).

权利要求:
Claims (27)
[0001]
1. Method of communication in a mobile network system, including an MME (103) or SGSN (111) mobility management node, an S-GW in-service gateway (104) serving as a bearer management node, and a P-GW packet data network gateway (105), characterized in that the packet data network gateway is connected to an external network (108) comprising: in case the mobility management node restart is performed, the bearer management node maintaining at least one bearer S5/S8 eligible for the restoration of communication services provided from the external network to a mobile terminal accommodated in the mobility management node; and the bearer management node removing another bearer(s).
[0002]
2. Communication method, according to claim 1, characterized in that it comprises: in case the bearer management node maintains the bearer(s) S5/S8, the bearer management node starts a timer, and the bearer management node removes the bearer resource(s) that the bearer management node holds on timer exhaustion.
[0003]
3. Communication method, according to claim 1, characterized in that it comprises: the bearer management node keeping the location registration area information of a mobile terminal notified from the mobility management node, and information identification associated with the mobile terminal.
[0004]
4. Communication method according to claim 3, characterized in that it comprises: upon receipt of an arrival to the mobile terminal after the mobility management node has restarted, the bearer management node notifies the management node arrival and location registration area information and identification information that the bearer management node maintains, and the mobility management node performs location using the identification information for an area corresponding to the area information of location record.
[0005]
5. Communication method, according to any one of claims 1 to 4, characterized in that it comprises: the bearer management node detects the restart of the mobility management node; the bearer management node confirming that the mobile terminal is accommodated in the mobility management node; and the bearer management node maintains, in connection with the mobile terminal, the bearer(s) S5/S8.
[0006]
6. Communication method, according to claim 1, characterized in that the mobility management node includes a first mobility management node associated with a first communication system and a second mobility management node associated with a second communication system, the method comprising: the mobile terminal location registration is performed on the first and second mobility management nodes, the bearer management node maintaining the mobile terminal location registration area information notified from the first and second mobility management nodes and the identification information associated with the mobile terminal, the bearer management node, in case of detection of restart of one of the first and second mobility management nodes, keep the bearer(s) (s) S5/S8; the bearer management node when receiving incoming data, send to one of the first and second reset mobility management nodes a notification message including the identification information associated with the mobile terminal as a destination of the incoming data and the information of location registration area, and one of the mobility management nodes restarted performing the location including identification information associated with the mobile terminal to an area corresponding to the location registration area information from the bearer management node.
[0007]
7. Communication method, according to claim 6, characterized by the fact that it comprises: in case the restart occurs in both of the first and second mobility management nodes, the bearer management node keeps all or a selected one of the bearers S5/S8; the bearer management node with incoming data sending to the first and second mobility management nodes a notification message including the identification information associated with the mobile terminal and the location registration area information; and the first and second mobility management nodes perform locating, inclusive of the identification information associated with the mobile terminal, for an area corresponding to the location registration area information from the bearer management node.
[0008]
8. Communication method, according to claim 1, characterized in that it comprises: the mobility management node informs one or a plurality of bearer management nodes about the latest location registration area information by event of mobile terminal mobility, and the bearer management node that detects the restart of the mobility management node by a health check mechanism keeps all selected bearers or bearer(s) and the identification information associated with the mobile terminal. mobile terminal along with location registration area information.
[0009]
9. Communication method, according to claim 8, characterized in that it comprises: the bearer management node starts a timer if it maintains the bearer(s), the identification information associated with the mobile terminal and the location registration area information, and the bearer management node removes the bearer(s), the identification information associated with the mobile terminal and the location registration area information that is maintained by the management node carrier, on timer expiration.
[0010]
10. Communication method, according to any one of claims 8 or 9, characterized in that it comprises: the bearer management node in the acquisition of data arriving at the mobile terminal, with the bearer, identification information and the information of location registration area of the mobile terminal being maintained by the bearer management node, sending to the mobility management node a notification message including the identification information associated with the mobile terminal and the location registration area information, and the mobility management node initiating location, including identification information associated with the mobile terminal, for all areas of location registration area information received from the bearer management node.
[0011]
11. Communication method, according to claim 10, characterized in that the mobile terminal initiates an attachment procedure upon receipt of the location.
[0012]
12. Mobile network system, characterized in that it comprises: an MME (103) or SGSN (111) mobility management node managing the mobility of a mobile terminal; an S-GW serving gateway (104) serving as a bearer management node; and a P-GW packet data network gateway (105) which is connected to an external network (108), where the bearer management node is adapted, in the event that a restart of the mobility management node is performed, to maintain at least one bearer S5/S8 eligible for re-establishment of communication services provided from the external network to a mobile terminal accommodated in the mobility management node, and remove other bearer(s).
[0013]
13. Mobile network system, according to claim 12, characterized in that by maintaining the bearer S5/S8, the bearer management node comprises means adapted to start a timer, and remove bearer resource(s) that the bearer bearer management node maintains, on timer exhaustion.
[0014]
14. Mobile network system, according to claim 12, characterized in that the bearer management node comprises means adapted to maintain: mobile terminal location registration area information notified by the mobility management node, and information identification associated with the mobile terminal.
[0015]
15. Mobile network system, according to claim 14, characterized in that when there is an arrival to the mobile terminal after the restart of the mobility management node, the bearer management node comprises means adapted to inform the mobility management node mobility management over arrival and over the identification information and location registration area information that the bearer management node maintains, and the mobility management node comprises means adapted to perform location, using the identification information, to an area corresponding to the location registration area information.
[0016]
16. Mobile network system, according to any one of claims 12 to 15, characterized in that upon detecting the restart of the mobility management node by the bearer management node, the bearer management node comprises means adapted to confirming that the mobile terminal is accommodated in the mobility management node, and the bearer management node comprises means adapted to maintain all bearers or at least a selected bearer of bearers S5/S8 in connection with the mobile terminal.
[0017]
17. Mobile network system, according to claim 12, characterized in that the mobility management node includes: a first mobility management node associated with a first communication system; and a second mobility management node associated with a second communication system, wherein the mobile terminal location registration is performed for the first and second mobility management nodes, the bearer management node comprising means adapted to maintain the location registration area information notified from the first and second mobility management nodes, and the identification information associated with the mobile terminal, the bearer management node upon subsequently receiving data coming to comprise means adapted to send to one of the first and second mobility management nodes restarting a notification message including the identification information associated with the mobile terminal as a destination of incoming data and location registration area information, and restarting one of the mobility management nodes understand adapted means to perform localization including information the mobile terminal identification to an area corresponding to the location registration area information 5 from the bearer management node.
[0018]
18. Mobile network system, according to claim 17, characterized in that in the event that both the first and second mobility management nodes are restarted, the bearer management node comprises means adapted to keep all bearers or a selected one. of bearers S5/S8, the bearer management node comprises means adapted to upon receiving the incoming data send a notification message including the identification information associated with the mobile terminal and the location registration area information to the first and second mobility management nodes, and the first and second mobility management nodes comprise means adapted to perform the location inclusive of the identification information associated with the mobile terminal to an area corresponding to the location registration area information from the mobile terminal carrier management.
[0019]
19. Mobile network system according to claim 12, characterized in that the mobility management node comprises means adapted to inform the bearer management node of the latest mobility event location registration area information of the mobile terminal, the bearer management node that detects the restart of the mobility management node by a health check mechanism comprises means adapted to keep all selected bearers or bearers and the identification information associated with the mobile terminal together with the location registration area information.
[0020]
20. Mobile network system, according to claim 19, characterized in that the bearer management node comprises means adapted to start a timer, in the case of keeping bearers, the identification information associated with the mobile terminal and the location registration area information, and the bearer management node comprises means adapted to remove the bearer(s), the identification information associated with the mobile terminal and the location registration area information that is held by the bearer management node, on timer exhaustion.
[0021]
21. Mobile network system according to any one of claims 19 or 20, characterized in that when obtaining the incoming data, the bearer management node comprises means adapted to send the mobility management node a notification message including of the identification information associated with the mobile terminal and the location registration area information, and the mobility management node comprises means adapted to initiate location, including the identification information associated with the mobile terminal, for all areas of the information of location registration area received from the bearer management node.
[0022]
22. Mobile network system, according to claim 21, characterized in that upon receipt of the location, the mobile terminal comprises means adapted to initiate an attachment procedure.
[0023]
23. Node appliance, managing bearers and functioning as an S-GW in-service gateway, in a mobile network system that includes an MME (103) or SGSN (111) mobility management node, said in-service gateway and a gateway P-GW packet data network gateway (105), characterized in that the packet data network gateway is connected to an external network (108), wherein the node apparatus comprises means adapted to maintain at least one bearer S5 /S8 eligible for re-establishing communication services provided from the external network to a mobile terminal accommodated in a mobility management node, and removing other carrier(s), when the mobility management node performs the restart the same.
[0024]
24. Node device, according to claim 23, characterized in that in case the carrier(s) S5/S8 is (are) maintained, the node device comprises means adapted to start a timer , and remove the held bearer resource(s), on timer exhaustion.
[0025]
25. Node apparatus, according to claim 23, characterized in that the node apparatus comprises means adapted to maintain: mobile terminal location registration area information notified from the mobility management node, and identification associated with the mobile terminal are maintained, whereby when the arrival at the mobile terminal is received after restarting the mobility management node, the node apparatus comprises means adapted to notify the arrival to the mobility management node, and the node apparatus comprises means adapted to notify the location registration area and identification information that is maintained by the node apparatus to the mobility management node.
[0026]
26. Node apparatus according to either of claims 23 or 25, characterized in that when it detects the restart of the mobility management node, the node apparatus comprises means adapted to keep all bearers or at least one selected bearer. of S5/S8 carriers.
[0027]
27. Node device, according to claim 25, characterized in that in case of maintenance of the bearer(s), the identification information associated with the mobile terminal and the location registration area information, the node apparatus comprises means adapted to initiate a timer, and the node apparatus comprises means adapted to remove the held bearer(s), the identification information associated with the held mobile terminal and the location record maintained.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112012019257B1|2022-01-25|Communication method, mobile network system, and node apparatus that manages a bearer

---

US9060374B2|2015-06-16|Communication method, mobile network system and device

---

US20120178479A1|2012-07-12|Communication method, mobile network system and device

同族专利:

---

公开号 | 公开日

---

CN102860052B|2015-11-25|

---

JP4968408B2|2012-07-04|

---

JP4962650B2|2012-06-27|

---

US20120202532A1|2012-08-09|

---

JP4968407B2|2012-07-04|

---

BR122016006460A2|2020-09-15|

---

JP2012080574A|2012-04-19|

---

EP2472991A1|2012-07-04|

---

JP2012075182A|2012-04-12|

---

JPWO2011136248A1|2013-07-22|

---

JP4962647B2|2012-06-27|

---

JP2012085338A|2012-04-26|

---

EP2466983A3|2012-07-04|

---

ES2505640T3|2014-10-10|

---

CN104936310A|2015-09-23|

---

JP4962648B2|2012-06-27|

---

JP2012105299A|2012-05-31|

---

JP2012080576A|2012-04-19|

---

JP4985880B2|2012-07-25|

---

BR122016006464A2|2020-09-15|

---

EP2472988A1|2012-07-04|

---

BR122016006463A2|2020-09-15|

---

KR101293339B1|2013-08-06|

---

KR101332971B1|2013-11-25|

---

EP2472990A1|2012-07-04|

---

JP4962655B2|2012-06-27|

---

US10595189B2|2020-03-17|

---

JP2012090319A|2012-05-10|

---

BR112012019257A2|2020-08-25|

---

JP2015159603A|2015-09-03|

---

EP2472992A1|2012-07-04|

---

JP2012085337A|2012-04-26|

---

JP2012100304A|2012-05-24|

---

EP2448299A1|2012-05-02|

---

KR20120095427A|2012-08-28|

---

US20120214519A1|2012-08-23|

---

ES2535361T3|2015-05-08|

---

JP2012055023A|2012-03-15|

---

JP2012100302A|2012-05-24|

---

EP2472988B1|2014-06-25|

---

JP4962644B2|2012-06-27|

---

EP2699048A1|2014-02-19|

---

EP2699048B1|2015-01-21|

---

ES2444815T3|2014-02-26|

---

JP2012080572A|2012-04-19|

---

BR122015021034A2|2020-09-15|

---

CN104936309B|2018-11-30|

---

JP2012065366A|2012-03-29|

---

CN104936310B|2019-04-16|

---

JP4962645B2|2012-06-27|

---

JP2012080573A|2012-04-19|

---

EP2472989A1|2012-07-04|

---

EP2448299B1|2013-10-30|

---

JP5967258B2|2016-08-10|

---

CN104936309A|2015-09-23|

---

JP2012151904A|2012-08-09|

---

JP4962651B2|2012-06-27|

---

US20190159012A1|2019-05-23|

---

EP2466983A2|2012-06-20|

---

EP2472990B1|2013-10-09|

---

EP2448299A4|2012-08-22|

---

US8923194B2|2014-12-30|

---

US20120300640A1|2012-11-29|

---

US9451583B2|2016-09-20|

---

US20170013666A1|2017-01-12|

---

BR122015021035A2|2020-09-15|

---

EP2472989B1|2013-09-04|

---

WO2011136248A1|2011-11-03|

---

US10231114B2|2019-03-12|

---

CN102860052A|2013-01-02|

---

US20160330786A1|2016-11-10|

---

US20150119089A1|2015-04-30|

---

US9763281B2|2017-09-12|

---

JP2012100303A|2012-05-24|

---

JP4962646B2|2012-06-27|

---

KR20130006713A|2013-01-17|

---

JP4968406B2|2012-07-04|

---

JP2012065367A|2012-03-29|

---

JP4962649B2|2012-06-27|

---

JP4962653B2|2012-06-27|

---

JP2012055024A|2012-03-15|

---

BR122016006458A2|2020-09-15|

---

US20120202496A1|2012-08-09|

---

EP2472991B1|2014-04-02|

---

JP4962652B2|2012-06-27|

---

JP4962654B2|2012-06-27|

---

ES2477566T3|2014-07-17|

---

US8514786B2|2013-08-20|

---

JP4968405B2|2012-07-04|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

DE60125424T2|2001-10-12|2007-09-27|Telefonaktiebolaget Lm Ericsson |METHOD FOR MAINTAINING USER DATA CONTAINED IN AN MSC / VLR AFTER RECOVERY OF THE SYSTEM|

---

ES2339746T3|2001-11-03|2010-05-25|Telefonaktiebolaget Lm Ericsson |METHOD AND NODE FOR THE ESTABLISHMENT OF A CONNECTION IN A TELECOMMUNICATION NETWORK.|

---

CN100550804C|2006-01-25|2009-10-14|华为技术有限公司|A kind of network attached method and network attachment system|

---

WO2007124685A1|2006-04-24|2007-11-08|Huawei Technologies Co., Ltd.|Paging medthod and apparatus in communication network|

---

CN101064932B|2006-04-24|2011-02-02|华为技术有限公司|Method for paging a plurality of users|

---

JP2008079311A|2006-09-21|2008-04-03|Asustek Computer Inc|Method and apparatus for detecting radio link failure in wireless communication system|

---

EP2137920A2|2007-01-12|2009-12-30|Nokia Corporation|Method and apparatus for providing automatic control channel mapping|

---

CN101707917A|2007-06-18|2010-05-12|诺基亚公司|Distributed scheduling for multicast in meshed wireless network|

---

CN101540719B|2008-03-19|2012-09-19|电信科学技术研究院|Method and equipment for re-locating serving gateway|

---

US8599765B2|2008-03-21|2013-12-03|Blackberry Limited|Evolved packet system quality of service enforcement deactivation handling to prevent unexpected user equipment detach|

---

US9001747B2|2008-03-26|2015-04-07|Nokia Corporation|Reporting channel state information|

---

CN101472256B|2008-04-03|2011-04-20|华为技术有限公司|Method for hanging up and recovering bearing as well as gateway proxy and communication system|

---

US8948768B2|2008-04-28|2015-02-03|Intel Mobile Communications GmbH|Radio communication device and method for controlling resource allocations|

---

JP5154693B2|2008-05-13|2013-02-27|サムスンエレクトロニクスカンパニーリミテッド|Voice call providing method and apparatus in mobile communication system and system thereof|

---

CN101610576B|2008-06-18|2013-01-30|上海华为技术有限公司|Information processing method under the condition of limiting signaling and related equipment|

---

JP5121624B2|2008-08-08|2013-01-16|株式会社エヌ・ティ・ティ・ドコモ|Mobile communication method and circuit switching center|

---

KR101029541B1|2008-08-11|2011-04-18|한국전자통신연구원|method for processing exceptional case of establishing default bearer in mobile communication system and device therefor|

---

US8243725B2|2008-08-13|2012-08-14|Interdigital Patent Holdings, Inc.|Maintaining circuit switched continuity in an enhanced universal terrestrial radio access network|

---

US20100080116A1|2008-09-29|2010-04-01|Qualcomm Incorporated|Re-establishing a radio resource control connection with a non-prepared base station|

---

CN101583192B|2008-10-14|2012-02-29|中兴通讯股份有限公司|Method for processing bearer reconstruction failure|

---

JP2010102166A|2008-10-24|2010-05-06|Konica Minolta Business Technologies Inc|Electrophotographic photoreceptor, image forming method, and image forming apparatus|

---

US8483149B2|2008-12-05|2013-07-09|Nokia Siemens Networks Oy|Resource allocation technique for physical uplink control channel blanking|

---

WO2010074441A2|2008-12-26|2010-07-01|Lg Electronics Inc.|Method of releasing radio bearer in wireless communication system and receiver|

---

KR101641096B1|2009-02-16|2016-07-20|삼성전자주식회사|Apparatus and method for managementing path between nodes in mobile communication system|

---

KR101528496B1|2009-04-17|2015-06-15|삼성전자주식회사|Method and system for supporting emergency call using non-access stratum protocol for emergency call in mobile telecommunication system|

---

WO2011038352A1|2009-09-26|2011-03-31|Cisco Technology, Inc.|Providing offloads in a communication network|

---

US8705445B2|2009-10-30|2014-04-22|Interdigital Patent Holdings, Inc.|Method and apparatus for efficient signaling and usage of resources for wireless communications supporting circuit switched and packet switched sessions|

---

EP2472990B1|2010-04-27|2013-10-09|Nec Corporation|Accelerating restoration of communication services upon MME restarting|

---

US20120178479A1|2010-04-27|2012-07-12|Nec Corporation|Communication method, mobile network system and device|

---

US20120172066A1|2010-04-27|2012-07-05|Nec Corporation|Communication method, mobile network system and device|

---

JP5342511B2|2010-06-16|2013-11-13|株式会社エヌ・ティ・ティ・ドコモ|Mobile communication method and call session control server device|

---

ES2526457T3|2010-06-17|2015-01-12|Telefonaktiebolaget Lm Ericsson |Paging requests issued by P-GW / GGSN|EP2371164B1|2008-12-19|2012-11-21|Telefonaktiebolaget L M Ericsson |GTP and GRE user-plane selection|

---

US9060374B2|2010-04-27|2015-06-16|Nec Corporation|Communication method, mobile network system and device|

---

EP2472990B1|2010-04-27|2013-10-09|Nec Corporation|Accelerating restoration of communication services upon MME restarting|

---

JP5011439B2|2011-01-07|2012-08-29|株式会社エヌ・ティ・ティ・ドコモ|Mobile communication method, mobility management node, and serving gateway device|

---

WO2011120453A2|2011-05-03|2011-10-06|华为技术有限公司|Method and device for receiving or transmitting short message|

---

US9161380B2|2011-07-19|2015-10-13|Qualcomm Incorporated|Silent redial during mobile-originated call|

---

JP2013150213A|2012-01-20|2013-08-01|Sharp Corp|Communication system, gateway device and communication method|

---

US10085207B2|2012-01-27|2018-09-25|Intel Corporation|Techniques for improved energy-savings management|

---

WO2013167160A1|2012-05-07|2013-11-14|Nokia Siemens Networks Oy|Speeding up user equipment reachability after network element restart|

---

US8923880B2|2012-09-28|2014-12-30|Intel Corporation|Selective joinder of user equipment with wireless cell|

---

EP2904826B1|2012-10-05|2017-03-08|Telefonaktiebolaget LM Ericsson |Report of serving network, time zone and uci|

---

EP2908582B1|2012-10-10|2019-06-19|LG Electronics Inc.|Processing paging by a server managing mobility to prevent, in case of paging failure, loss of downlink data buffered in a serving gateway|

---

CN104823513A|2012-12-14|2015-08-05|富士通株式会社|Wireless communication system, mobile terminal, server, and wireless communication method|

---

US9807548B2|2013-02-01|2017-10-31|Alcatel Lucent|Method and system for obtaining location information from a wireless network|

---

JP5525092B1|2013-04-05|2014-06-18|日本電気株式会社|Mobility management device, communication system, voice incoming call control method, and program|

---

JP5606603B1|2013-05-20|2014-10-15|日本電気通信システム株式会社|Mobile communication system, SGW, terminal, communication method and control method|

---

JP6221716B2|2013-12-11|2017-11-01|富士通株式会社|Communication system and network device|

---

US9999020B2|2014-01-13|2018-06-12|Lg Electronics Inc.|Downlink data transfer method and location update procedure execution method|

---

CN104853338A|2014-02-14|2015-08-19|中国移动通信集团广东有限公司|Business continuing method, device, and mobile switching center / visitor location register|

---

CN105359591B|2014-02-21|2019-08-13|华为技术有限公司|A kind of processing method and equipment of network failure|

---

CN104883668B|2014-02-28|2020-02-21|北京三星通信技术研究有限公司|Method for supporting PWS quick recovery|

---

US9369937B1|2014-07-11|2016-06-14|Sprint Communications Company L.P.|Long term evolutionnetwork hand-over control based on quality-of-service class indicatorcombinations|

---

CN105744502A|2014-12-08|2016-07-06|中兴通讯股份有限公司|Intelligent paging method and system, serving gateway and mobile management entity|

---

EP3240329A4|2014-12-22|2018-07-11|Nec Corporation|Mobile communication system, sgw, terminal, incoming method for mobile communication system, incoming method for sgw, and incoming method for terminal|

---

KR20170128540A|2015-03-27|2017-11-22|후아웨이 테크놀러지 컴퍼니 리미티드|Data transmission method, access network device, and communication system|

---

KR101735382B1|2015-10-16|2017-05-15|주식회사 엘지유플러스|Method and apparatus for providing incoming call service during MME fault|

---

JP2018074522A|2016-11-02|2018-05-10|日本電気株式会社|Gateway device, mobility management device, base station, communication method, control method, paging method, and program|

---

CN106972963B|2017-03-23|2020-01-03|数据通信科学技术研究所|Service module starting control method and starting control method after crash restart|

---

JP6873943B2|2018-03-26|2021-05-19|Kddi株式会社|Terminal equipment, base station equipment, control methods, and programs that enable location registration processing during sleep mode.|

---

US11109344B2|2019-05-01|2021-08-31|Lg Electronics Inc.|Start and stop of reception of downlink transmission based on paging|

---

CN110312323B|2019-05-21|2021-01-08|展讯半导体有限公司|Control method, control device and storage medium|

---

CN113098822A|2019-12-20|2021-07-09|华为技术有限公司|Method and device for recovering IMS service|

法律状态:
2020-09-01| B15K| Others concerning applications: alteration of classification|Free format text: AS CLASSIFICACOES ANTERIORES ERAM: H04W 8/08 , H04W 24/04 , H04W 92/24 Ipc: H04W 76/19 (2018.01), H04W 76/25 (2018.01), H04W 7 |

---

2020-09-01| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2021-11-23| B350| Update of information on the portal [chapter 15.35 patent gazette]|

---

2021-12-14| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2022-01-25| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 27/04/2011, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF, QUE DETERMINA A ALTERACAO DO PRAZO DE CONCESSAO. |

优先权:

---

申请号 | 申请日 | 专利标题

---

JP2010102166|2010-04-27|

---

JP2010-102166|2010-04-27|

---

PCT/JP2011/060215|WO2011136248A1|2010-04-27|2011-04-27|Communication method, mobile network system and apparatus|BR122015021034-8A| BR122015021034A2|2010-04-27|2011-04-27|MOBILE TERMINAL AND METHOD FOR REGISTERING A MOBILE TERMINAL|

---

BR122016006458-1A| BR122016006458A2|2010-04-27|2011-04-27|MOBILE TERMINAL AND METHOD FOR REGISTERING A MOBILE TERMINAL|

---

BR122016006464-6A| BR122016006464A2|2010-04-27|2011-04-27|MOBILE TERMINAL AND METHOD FOR REGISTERING A MOBILE TERMINAL|

---

BR122015021035-6A| BR122015021035A2|2010-04-27|2011-04-27|OVEL|

---

BR122016006460-3A| BR122016006460A2|2010-04-27|2011-04-27|MOBILE TERMINAL AND METHOD FOR REGISTERING A MOBILE TERMINAL|

---

BR122016006463-8A| BR122016006463A2|2010-04-27|2011-04-27|MOBILE TERMINAL AND METHOD FOR REGISTERING A MOBILE TERMINAL|